Update firebase-tools to the latest version 馃殌 - #9
Open
greenkeeper[bot] wants to merge 1 commit into
Open
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 4.0.0 of firebase-tools was just published.
The version 4.0.0 is not covered by your current version range.
If you don鈥檛 accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of firebase-tools.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don鈥檛 have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.0.0firebase deploywill now ask for confirmation before Cloud Functions deletion. Running the command with--non-interactivewill fail if there are functions detected for deletion."engines": {"node": "8"}tofunctions/package.json. You will needfirebase-functionsSDK v2.0.0 or up.firebase functions:deletecommand for explicit deletion of functions.firebase initover-wrote existing Firestore rules and indexes that were either specified through a local file or specfied in the Firebase Console.Commits
The new version differs by 13 commits.
69776f2[firebase-release] Updated CLI to 4.0.03582612Changelog for v4.0.0 (#294)c4c17d3Update firebase init template for functions (#293)85deaf9Display Node version that functions are deployed to (#291)1f41e01Support Node.js 8 functions runtime. (#290)5fd8ae0Ask for confirmation before deleting functions during 'firebase deploy' (#287)46511c5Add "firebase functions:delete" command (#286)f9d3460Support configuration of function region, memory, and timeout (#285)b35592dDefault JS linting to false duringfirebase initfor functions (#836)6ce81c0Fix bug where "firebase init" overwrites existing Firestore indexes (#832)7ec8b0bFix bug where "firebase init" overwrote existing Firestore rules (#831)1c1b372Update profiler to new query format (#826)0ff6a55[firebase-release] Removed change log and reset repo after 3.19.3 releaseSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 馃尨